翻訳と辞書
Words near each other
・ Progress M-2
・ Progress M-20M
・ Progress M-21M
・ Progress M-22M
・ Programming ethics
・ Programming game
・ Programming idiom
・ Programming in the large and programming in the small
・ Programming interview
・ Programming language
・ Programming Language Design and Implementation
・ Programming Language for Business
・ Programming language generations
・ Programming language implementation
・ Programming language reference
Programming language specification
・ Programming language theory
・ Programming languages used in most popular websites
・ Programming Linux Games
・ Programming Metadata Communication Protocol
・ Programming paradigm
・ Programming Perl
・ Programming productivity
・ Programming Research Group
・ Programming Research Limited
・ Programming Ruby
・ Programming Station
・ Programming style
・ Programming team
・ Programming the Nation?


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Programming language specification : ウィキペディア英語版
Programming language specification
In computing, a programming language specification (or standard or definition) is a documentation artifact that defines a programming language so that users and implementors can agree on what programs in that language mean. Specifications are typically detailed and formal, and primarily used by implementors, with users referring to them in case of ambiguity; the C++ specification is frequently cited by users, for instance, due to the complexity. Related documentation includes a programming language reference, which is intended expressly for users, and a programming language rationale, which explains why the specification is written as it is; these are typically more informal than a specification.
==Standardization==
Not all major programming languages have specifications, and languages can exist and be popular for decades without a specification. A language may have one or more implementations, whose behavior acts as a ''de facto'' standard, without this behavior being documented in a specification. Perl (through Perl 5) is a notable example of a language without a specification, while PHP was only specified in 2014, after being in use for 20 years.〔(Announcing a specification for PHP ), July 30, 2014, Joel Marcey〕 A language may be implemented and then specified, or specified and then implemented, or these may develop together, which is usual practice today. This is because implementations and specifications provide checks on each other: writing a specification requires precisely stating the behavior of an implementation, and implementation checks that a specification is possible, practical, and consistent. Writing a specification before an implementation has largely been avoided since ALGOL 68 (1968), due to unexpected difficulties in implementation when implementation is deferred. However, languages are still occasionally implemented and gain popularity without a formal specification: an implementation is essential for use, while a specification is desirable but not essential (informally, "code talks").

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Programming language specification」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.